Remote control button actuation module, system, and method

ABSTRACT

A device that can house a remote control for activating or controlling one or more features or functions of a vehicle. The device securely holds the remote control and upon reception of a command, operates to control a boom, actuator and pin such that the pin is moved over a particular button of the remote control, and then pressed for a requested period of time. A serious of commands or complex commands can result in causing multiple pressing patterns of the various buttons of the remote control. Thus, the features or functions of the vehicle can be activated remotely.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a non-provisional application being filed in the United StatesPatent Office under 35 USC 111 and claims priority under 35 U.S.C.§119(e) to the U.S. provisional application entitled “REMOTE CONTROLBUTTON ACTUATION SYSTEM,” filed on Dec. 24, 2013, and assignedapplication Ser. No. 61/920,494, the entire contents of which are herebyincorporated by reference.

BACKGROUND

Electronic systems in automotive vehicles and other devices may utilizehandheld remote controls with finger-pressable buttons. These devicescan be utilized to remotely actuate vehicle or device functions by hand,where such functions may be difficult to access otherwise by a vehicleoperator. The remote controls of these electronic systems generallypermit secure remote actuation of unlocking, locking, power door andtrunk opening, remote engine starting, activation of horns, lights andpanic features as well as other types of vehicle or device functions.

In recent years, the rapid and widespread growth in long-range wirelessconnectivity and sophisticated hand-held mobile devices with touch-typegraphical user interfaces and short or long-range wireless connectivityhas led to the proliferation of machine-to-machine connectivitysolutions and “anywhere at any time” device interactivity. Consumers nowexpect all of their vehicles, homes and devices to be connected and ableto be interacted with via their mobile technology from anywhere and atany time.

An increasing number of new vehicles come equipped with built-inwireless connectivity that enables connectivity to these vehicles viamobile devices and web-enabled devices for remote function actuation.Vehicles from General Motors, for example, equipped with ONSTARtelematics connectivity can be remotely started or unlocked with asmartphone running a downloaded software application (“app”). This is aproprietary, designed-in solution available only to purchasers of thesevehicles and requires the purchase of an ongoing subscription fromONSTAR for the cellular data connectivity to the vehicle to enable thisfunction.

It is generally known that vehicle electronics suppliers have beenoffering retrofitted systems to expand the remote control capabilitiesavailable to vehicle owners. Directed Electronics, for example, offersaftermarket systems that control more functions and provide longer-rangeof connectivity, including the addition of telematics communications forcontrol from any location with a smartphone application. One primarylimitation of these systems includes the need for extensive customengineering efforts to enable the electronics to interface to and workwith the electronics of the vehicles. In addition, consumers may berequired to employ a professional technician for all installationefforts due to the technical complexity of the different vehicleinstallations. Consequently, these installations are generally expensivefor consumers to consider.

More recently, suppliers of aftermarket vehicle electronics haveintroduced systems that consumers can self-install at low-cost andcomplexity. Delphi Automotive, for example, has recently introduced asystem that can be plugged into a standardized on-board diagnostics(OBD-II) connector found on all light-duty vehicles since 1996. Thevehicle owner can easily install the system and, after downloading asmartphone application, can have remote control of vehicle accessfunctions from their smartphone or a web-enabled device. By leveragingfeatures found standard in many vehicles, this system advantageouslyallows for the addition of a new radio-frequency (RF) transmitter tooperate as a secure remote control using procedures built into thevehicle by its manufacturer. Other suppliers are attempting to reverseengineer data bus commands for each vehicle to permit long-range remotecontrol of the functions of the vehicle by transmitting data buscommands onto the OBD-II connector from a consumer-installed device. Themain limitations of the RF control technique are that many vehicles donot have any available method for adding a new transmitter by the owner.Additionally, many vehicles have such sophisticated secure RF designsthat no method can be found practically to transmit the proper securecodes to a vehicle.

The main limitation of a data bus control technique is the extensiveeffort to reverse-engineer data bus commands for each vehicle.Additionally, many vehicles cannot be controlled via this connector atsome or all of the time, such as when an owner is away from theirvehicle due and/or due to a lack of available data bus commands.

U.S. Patent Publication No. 2009/0108989 A1 describes a remote controlactuation system using a controller and solenoid(s) to press one or tworemote control actuation buttons of a vehicle remote control. The systemwould be placed in a location within the confines of the vehicle. The'989 application describes an actuation method specific to a single typeof remote control with a specific button location layout. The '989application does not describe a configurable, or adaptable, system formounting or actuating more than 2 buttons. The '989 application alsofails to accommodate the numerous and widely-varying remote controlmulti-button designs found on vehicle remote control fobs, for example.Vehicle remote controls can have from 2 to 8 buttons in any type oflayout and orientation on up to 3 surface planes of the remote control,varieties of package sizes and designs without a mechanical key bladeand ones with fixed or movable mechanical key blades.

The '989 application also fails to provide for the linkage of remotecontrol actuation to a user's mobile devices, e.g., a mobile smartphoneapplication. Furthermore, the '989 application fails to describe atechnique for blocking the vehicle detection of the remote controlwithin the vehicle by low-frequency techniques used in vehicleimmobilization or push-button engine start features. It is generallyunderstood that vehicles and their remote controls can include alow-frequency circuitry that enables secure detection of the presence ofthe remote control within the vehicle. As such, blocking the RF functionof the remote control and detection of the presence of the remotecontrol can be used to prevent or alleviate the vehicle from being atarget of drive-away theft.

Therefore, there is a need in the art for a remote control to controlthe functions of a vehicle and/or other device, specifically for asingular design for wireless connectivity enhancements of linkage tomobile devices which can be added to all existing vehicle or deviceremote control systems without special tools or training.

BRIEF SUMMARY

The presently disclosed embodiments, as well as features and aspectsthereof, are directed towards a remote control button actuation machinethat includes a button actuator tip mounted on a rotatable andextendable boom that is configurable to actuate the buttons on a remotecontrol for vehicle or device. The button actuator tip can be moved toany position over the surface of the remote control by actuating firstand second servo motors operably linked to the boom to control boomrotation angle and boom extension distance. Once positioned over aremote control button, the button actuator tip, operably linked to athird servo motor, may be lowered to press a remote control button. Theservo motors may be controlled by a programmable controller thatreceives signals from either a mobile device via short or medium-rangewireless signals or from a separate telematics gateway device whichextends the range of control to the mobile device.

The various embodiments of the controller may include configurablenonvolatile memory that can provide storage of data, such as datarepresentative of the proper servo positions for all buttons on aninstalled vehicle or device remote control. The data may be loaded intothe memory of the controller at manufacture, programmed after sale byusing a one-time calibration process performed by a user, selectable orgenerated upon the entrance of a code, down loadable, etc. The systemmay be powered by an internal power supply using either internal orexternal batteries, or may be powered by interfacing to another powersource such as a 12-volt source available in the vehicle. A casing orholder can secure the remote control in place, for actuation by themachine, such as by using a clamping system with pads held tightly underspring tension and opened for remote control placement between theclamping pads by a simple linear motion on a clamp arm. The system withthe included remote control may be located within a vehicle in a hiddenlocation to prevent theft. Alternatively or in addition to, the systemcan be located proximate or near the controlled device.

In another embodiment, the machine and/or controller may be operated byremote control and thus this disclosure includes a method to calibrateand operate the remote control machine and controller by RF means or anyform of wireless transmission including but not limited to theunlicensed spectrum, BLUETOOTH, WIFI, etc.

Another embodiment includes a method of remotely actuating the buttonsof a remote control by mounting a remote control with actuatable buttonsin proximity to a machine to actuate buttons of the remote control. Anexemplary machine may include a rotatable pivot secured to a base and aboom comprising a first end and second end. The boom is mounted, e.g.,rotatably mounted on the rotatable pivot at the first end and reversiblyextendable from the pivot. An actuator is fixedly mounted on the secondend. The pivot, the boom and the actuator are configurable to raise andlower a tip to actuate the buttons of the remote control. Anotherembodiment includes a computer program product that includes a computerreadable medium having computer readable code embodied therein. In suchan exemplary embodiment, the computer readable program code is adaptedto be executed by a processor to implement a method of remotelyactuating the buttons of a remote control. When executed, the computerreadable code causes the computer and/or devices interfaced thereto toactuate buttons, switches or actuators of a a remote control mounted toa holder and proximate to a actuation machine.

In an embodiment, the machine includes a rotatable pivot secured to abase and a boom comprising a first end and second end. The boom isrotatably mounted on the rotatable pivot at the first end and reversiblyextendable from the pivot. An actuator is fixedly mounted on the secondend, and wherein the pivot, the boom and the actuator are configurableto raise and lower a tip to engage the buttons of the remote control.

In an alternative embodiment, an exemplary machine may include a boommounted on a rotatable pivot, which rotatable pivot is secured to abase, and a button actuator assembly slidable along the boom. The pivot,the boom and the button actuator assembly are configurable to raise andlower a tip to actuate the buttons of the remote control.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

In the Figures, like reference numerals refer to like parts throughoutthe various views unless otherwise indicated. For reference numeralswith letter character designations such as “102A” or “102B”, the lettercharacter designations may differentiate two like parts or elementspresent in the same Figure. Letter character designations for referencenumerals may be omitted when it is intended that a reference numeral toencompass all parts having the same reference numeral in all Figures.

FIG. 1 is a mechanization diagram showing exemplary components of anembodiment of the remote button actuation system.

FIG. 2 is a right-side isometric view of the remote button actuationsystem of FIG. 1 constructed in accordance with the description with theenclosure not shown.

FIG. 3 a is a left-side isometric view of the remote button actuationsystem of FIG. 2.

FIG. 3 b is the view of FIG. 3 a with z-axis servo motor and z-axisdrive gear hidden from view.

FIG. 4 is a bottom-side isometric view showing the remote control holderof the system of FIGS. 2 and 3.

FIG. 5 is a top-side isometric view showing the entire system of FIGS. 2and 3 showing the enclosure housing with a remote control clamped withinthe remote control holder.

FIG. 5 a is a bottom-side isometric view showing the entire system ofFIGS. 2 and 3.

FIG. 6 is a view of the calibration guide.

FIG. 7 is a right-side isometric view of the calibration guide installedover the calibration guide alignment pins of the remote button actuationsystem of FIGS. 2 and 3 with the 3-axis actuator not shown.

FIG. 8 is a flowchart describing the calibration of the remote controlbutton actuator of FIGS. 2 and 3.

FIG. 9 is a flowchart describing the operation of the remote controlbutton actuator of FIGS. 2 and 3.

FIG. 10 is a schematic diagram illustrating an exemplary architecturefor remote control actuating embodiments.

FIG. 11 is a functional block diagram illustrating an exemplary,non-limiting aspect of a portable computing device (“PCD”) in the formof a wireless telephone for implementing the remote control actuationmethods and systems; and

FIG. 12 is a schematic diagram illustrating an exemplary softwarearchitecture for remote control actuating embodiments.

FIG. 13 is a left-side isometric view of an alternative embodiment ofthe remote button actuation system.

FIG. 14. is a right-side isometric view of an alternative embodiment ofthe remote button actuation system.

FIG. 15 is a front-side isometric view of an alternative embodiment ofthe remote button actuation system.

FIG. 16 is a front-side isometric view of an alternative embodiment ofthe remote button actuation system with a remote control positioned inan actuatable configuration.

FIG. 17 is a top-view of the system and remote control of FIG. 16enclosed in a box.

DETAILED DESCRIPTION

Aspects, features and advantages of several exemplary embodiments of theremote button actuation system will become better understood with regardto the following description in connection with the accompanyingdrawing(s). It should be apparent to those skilled in the art that thedescribed embodiments of the present description provided herein areillustrative only and not limiting, having been presented by way ofexample only. All features disclosed in this description may be replacedby alternative features serving the same or similar purpose, unlessexpressly stated otherwise. Therefore, numerous other embodiments of themodifications thereof are contemplated as falling within the scope ofthe present description as defined herein and equivalents thereto.Hence, use of absolute terms such as, for example, “will,” “will not,”“shall,” “shall not,” “must” and “must not” are not meant to limit thescope of the present description as the embodiments disclosed herein aremerely exemplary.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as exclusive, preferred oradvantageous over other aspects.

In this description, the term “application” may also include fileshaving executable content, such as: object code, scripts, byte code,markup language files, and patches. In addition, an “application”referred to herein, may also include files that are not executable innature, such as documents that may need to be opened or other data filesthat need to be accessed.

The term “content” may also include files having executable content,such as: object code, scripts, byte code, markup language files, andpatches. In addition, “content,” as referred to herein, may also includefiles that are not executable in nature, such as documents that may needto be opened or other data files that need to be accessed.

As used in this description, the terms “component,” “database,”“module,” “system,” “thermal energy generating component,” “processingcomponent” and the like are intended to refer to a computer-relatedentity, either hardware, firmware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a computing device and the computing device may be a component. Oneor more components may reside within a process and/or thread ofexecution, and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentsmay execute from various computer readable media having various datastructures stored thereon. The components may communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems by way of the signal).

In this description, the terms “communication device,” “wirelessdevice,” “wireless telephone,” “wireless communication device” and“wireless handset” are used interchangeably. With the advent of thirdgeneration (“3G”) and fourth generation (“4G”) wireless technology,greater bandwidth availability has enabled more portable computingdevices with a greater variety of wireless capabilities.

In this description, the terms “workload,” “process load” and “processworkload” are used interchangeably and generally directed toward theprocessing burden, or percentage of processing burden, associated with agiven processing component in a given embodiment. Further to that whichis defined above, a “processing component” or “thermal energy generatingcomponent” may be, but is not limited to, a central processing unit, agraphical processing unit, a core, a main core, a sub-core, a processingarea, a hardware engine, etc. or any component residing within, orexternal to, an integrated circuit within a portable computing device.Moreover, to the extent that the terms “thermal load,” “thermaldistribution,” “thermal signature,” “thermal processing load” and thelike are indicative of workload burdens that may be running on aprocessing component, one of ordinary skill in the art will acknowledgethat use of these “thermal” terms in the present disclosure may berelated to process load distributions and burdens.

In this description, the term “portable computing device” (“PCD”) isused to describe any device operating on a limited capacity powersupply, such as a battery. Although battery operated PCDs have been inuse for decades, technological advances in rechargeable batteriescoupled with the advent of third generation (“3G”) wireless technologyhave enabled numerous PCDs with multiple capabilities. Therefore, a PCDmay be a cellular telephone, a satellite telephone, a pager, a PDA, asmartphone, a navigation device, a smartbook or reader, a media player,a combination of the aforementioned devices, a laptop computer with awireless connection, among others.

FIG. 1 shows a mechanization diagram of the remote control buttonactuation system in accordance with the description. In one embodimentthe controlling system 100 may be a wireless mobile device, whichoperates to send user commands via wireless RF or other wirelesstechnology, including optical and audible technology, directly to thecontroller and power supply 8. It will be appreciated that throughoutthis description, the term RF or RF wireless are used but, in all suchinstances unless specifically mentioned otherwise, any wireless or wiredtechnology could also be utilized in such situations. In anotherembodiment, the controlling system 100 may be a gateway device locatedwithin the vehicle or nearby the device under control and, whichconnects wirelessly via RF or via wires to the controller and powersupply 8. The controller and power supply 8 receives an actuationcommand from the controlling system 100. The actuation command mayinclude a variety of information and one such example is to include theidentity of a particular remote control button that is to be actuatedand a specific duration of time to actuation the button. The commandsmay include a variety of other information such as, time of day toactuate the button, a sequence of buttons to be actuated, a request formultiple presses of a single button, etc. The controller and powersupply 8 converts these commands into specific servo motor commands thatcause the provision of actuating power to the 3-axis button actuationsystem 51, which presses the selected remote control 101 button for therequired duration and then releases the button, or otherwise performsthe requested command. It will be appreciated that in some embodiments,the pivot arm may include multiple tips and a further servo could beused to control the relative location of the multiple tips. Forinstance, if a certain function requires two buttons to be pressedsimultaneously, the server could operate to position the tips relativeto each other at a certain distance to ensure actuation of both buttons.When only a single button needs to be actuated, the servo can move theadditional tip out of the way or, bring all the tips in to closeproximity such that they operate as a single tip.

FIG. 2 is a right-side isometric view of an exemplary 3-axis buttonactuation system 51. A button actuator tip 1 is attached to a z-axisrack gear 2, which is held in position by a motor support bracket 28 andattached to a sliding boom 4. The tip 1 can be moved vertically when thez-axis pinion gear 3 rotates. Z-axis pinion gear 3 is attached to oneend of a z-axis driveshaft 5, which extends longitudinally through theentire length of sliding boom 4. Sliding boom 4 is held by boom support10, which enables the sliding boom to move horizontally to repositionbutton actuator tip 1. Boom support 10 rotates about the vertical axison boom support pivot pin 47, which is attached to the mountingenclosure 50 shown in FIG. 5. Angle-axis driven gear 6 is also mountedto the boom support pivot pin 47 and the enclosure 50. Angle-axis servomotor 9 is attached to boom support 10 and rotates angle-axis drive gear7, which is engaged with angle-axis driven gear 6.

Remote control clamp pad 30 is mounted on clamp pad pivot pin 31, whichis attached to one end of clamp pad support 38. Clamp pad 36 and clamppad pivot 37 are mounted to the opposite end of clamp pad support 38.Clamp pad support 38 is mounted to clamp pad support pivot pin 40, whichrotates on spring bracket 42. Clamp pad 32 is mounted on clamp pad pivotpin 33 and which is attached to one end of clamp pad support 39. Clamppad 34 and clamp pad pivot 35 are mounted to the opposite end of clamppad support 39. Clamp pad support 39 is mounted to clamp pad supportpivot pin 41, which rotates on spring bracket 43. Clamp pad tensionspring 44 mounts to one end of spring bracket 42 and spring bracket 43.Clamp pad tension spring 45 mounts to the opposite ends of springbracket 42 and spring bracket 43. Clamp pad tension release control armand cam 46 is mounted to the enclosure 50 and rotates about the verticalaxis to rotate the cam against the spring brackets 42 and 43. The clamppad support pivot pins 40 and 41 move in the clamp pad support slideholes 57 and 58 of FIG. 5 a in the enclosure 50.

FIG. 3 a is a left-side isometric view of the 3-axis button actuationsystem 51 constructed in accordance with one embodiment. Z-axis drivengear 24 is attached to the opposite end of z-axis driveshaft 5 from thez-axis pinion gear 3. Z-axis servo motor 22 rotates z-axis drive gear 23which is engaged with z-axis driven gear 24. R-axis rack gear 25 isattached longitudinally to the top of boom support 10. R-axis piniongear 26 engages with r-axis rack gear 25 and is rotated by r-axis servomotor 20. Z-axis servo motor 22 and r-axis servo motor 20 are bothmounted to the surface of motor support bracket 28 which is, in turn,mounted to each end of the sliding boom 4. FIG. 3 b is a left-side viewof FIG. 3 a with z-axis servomotor 22 and z-axis drive gear 23 removed.Sliding boom anti-rotation pin 29 is attached to boom support 10 andslides in a slot in motor support bracket 28 to prevent rotation ofsliding boom 4 when it is moving longitudinally within the boom support10.

FIG. 4 is a bottom-side isometric view of the 3-axis button actuationsystem 51 constructed in accordance with one embodiment. FIG. 5 is atop-side isometric view of the controller and power supply 8 and 3-axisbutton actuation system 51 mounted with the housing 50 and constructedin accordance with one embodiment. Remote control 101 is shown mountedwithin the 3-axis button actuation system 51 and held firmly in place byclamp pads 30, 32, 34 and 36 by clamp pad tension springs 44 and 45.Calibration guide alignment pins 52, 53, 54 and 55 are shown protrudingfrom the inside bottom surface of housing 50. FIG. 6 shows transparentcalibration guide 56 used in one embodiment. FIG. 7 shows calibrationguide 56 mounted on calibration guide alignment pins 52, 53, 54 and 55using holes at each corner of calibration guide 56. The installed remotecontrol 101 is located just below the calibration guide 56.

FIG. 8 is a flowchart describing the calibration process for the 3-axisbutton actuation system 51 according to one embodiment. FIG. 9 is aflowchart describing the operation process for the 3-axis buttonactuation system 51 according to one embodiment.

In other embodiments, servo gears, pinions and racks could be replacedwith link arms and linkages to transfer rotational forces and causerotational and linear motions of the 3-axis button actuation system 51.The z-axis servo and gears could be replaced by a two-position solenoidto move the button actuator tip 1 vertically. The fixed-length slidingboom 4 and z-axis driveshaft 5 could be replaced by telescoping elementsas a means to conserve enclosure 50 space. An alternative method ofmoving the button actuation tip 1 over the remote control 101 buttonarea could be constructed using x-axis and y-axis servo motors with anx-y sliding table. To enable compatibility with remote controls 101which have buttons on more than one surface, such as sides or bottom,the addition of adjustable levers and pivot points would enable thedownward button actuator tip 1 motion to be translated into lateral orupward forces for pressing those buttons. For remote controls which haveadditional RF circuitry for use in secure remote control presencedetection by a vehicle or device to enable functions such as enablingengine start, these RF detection functions may need to be blocked toprevent detection of the remote control in the presence of the vehicleor device. RF blocking materials in the housing could be used topassively prevent detection or active RF circuitry, including an antennaand transmitter could be used to, under controller and power supply 8command, activate or deactivate RF blocking.

FIG. 13, FIG. 14, FIG. 15, FIG. 16 and FIG. 17 show an alternativeembodiment, i.e., machine 400 comprising boom 402 that is mounted tofixed shaft 408 proximate to pivot end 404. Fixed shaft 408, fixedlymounted on box 600, passes through an opening (not shown) in boom 402.One or more bushings (not shown) positioned between boom 402 and fixedshaft 408 allow the boom to rotate about fixed shaft 408 such that boomdistant end 406 moves along arcuate path 412. Servo motor 414 is linkedto drive gear 416A that engages pivot gear 416B to move boom 402 aboutaxis 410. Button actuator 418 is slidable along boom 402. Lever 422 ismechanically coupled to the actuator by arm 424. Gates 420A and 420B,formed in the housing of actuator 418, limit the movement of actuator418 along the length of boom 402. Lever 422 is driven by servo motor 426to which lever 422 is mechanically linked. Downward button actuator tip428 is reversibly driven by gear 430. Gear 430 is driven by a thirdservo motor 446.

Remote control 500 is held proximate to machine 400 by pads 432, 434,438, and 440. Pads 432 and 434 are resiliently biased against remotecontrol 400 by member 436. Pads 438 and 440 are resilient biased againstan opposite side of remote control 500 by member 444. Members 442 and444 are anchored to box 600, e.g., to walls 602 and 604, respectively.

Thus, it is clear from the above-presented embodiments of the remotecontrol button actuator system that some embodiments utilize a 3-axisservo-controlled actuator to permit universal remote control actuationwith a plurality of buttons to be actuated. In addition, the embodimentspresent the use of a spring-loaded, adjustable remote control holder soas to facilitate the adjustment of any type of remote control.Advantageously, the remote control actuation system alleviates, and insome instances, eliminates the problem encountered by other systemswhich attempt to take control of devices (e.g. automotive keyless entry)via hard-wired or RF methods and which require extensive reverseengineering on a vehicle-by-vehicle basis or sacrificing of expensiveremote controls which are used for code harvesting. Furthermore, thedescribed embodiments of the actuation system do not require the use ofdedicated solenoids for each remote button on the remote controller.Further, the various embodiments do not require special brackets ortooling to hold different types of remotes.

Operation

In operation, a user connects the controlling system 100 to thecontroller and power supply 8 either using a wireless RF or wiredconnection. Software applications running within the user's mobiledevice and controlling system 100 operate to provide remote control ofthe controller and power supply 8. The first-time setup process wouldinvolve preparing the controller and power supply 8 and 3-axis buttonactuation system 51 for remote control 101 installation by the user. Thebutton actuator tip 1 would be retracted and moved out of the way topermit remote control 101 installation. The user would move the clamppad tension release control arm and cam 46, causing the cam to actagainst the spring brackets 42 and 43 to move the clamp pads 30, 32, 34and 36 outward. The remote control 101 can then be placed between theclamp pads and the clamp pad tension release control arm and cam 46would be moved back to place the remote control 101 under tension fromclamp pad tension springs 44 and 45. It should be appreciated that insome embodiments, specific holders that are designed to receive specificremote control models may be utilized rather than the clamp. Further,the system may include an interface for receiving one of a plurality ofspecific holders such that a specific holder can be installed for aspecific application.

With reference to FIGS. 13-17, in the alternative exemplary embodiment,remote control 500 is resiliently biased against pads 432, 434, 438, and440 and fitted into position under the actuation device 400. Servomotors 414 and 426 position actuator tip 1 (not shown) over theappropriate button on remote control 500. A third servo motor 446 drivesdown the rack gear on downward button actuator tip 428, thus actuatingthe desired button. The alternative exemplary embodiment may also beprogrammed according to the steps and description for the embodiments ofFIGS. 1-12.

The transparent calibration guide 56 would be placed and aligned overthe calibration guide alignment pins 52, 53, 54 and 55. The user wouldmake a mark with a fine-tipped marker on the calibration guide over thecenter of every remote control 101 button. The calibration guide wouldbe removed and the numbered intersecting lines closest to each markidentified for the angle-axis and r-axis settings for each button.

FIG. 8 shows the calibration procedure 200 which would be performed bythe user in conjunction with a software application running on a mobiledevice, beginning with step 201. For each of n buttons on a user'sremote control, a series of steps may be followed. Step 202 initiates abutton counter for the first button. Step 203 uses the angle-axiscalibration value from the calibration guide 56 for the current buttonto drive the angle-axis servomotor 9 to that value. Step 204 uses ther-axis calibration value from the calibration guide 56 for the currentbutton to drive the r-axis servo motor 20 to that value. Step 205 hasthe user activating the z-axis servo motor 22 to lower the buttonactuator tip 1 until it just contacts the current remote control 101button. The user would visually examine the location of the buttonactuator tip 1 and determine if it were properly centered over thebutton. If not, step 206 shows how the user would use the application tomake minor adjustments in angle-axis and/or r-axis servo values tocenter the button actuator tip 1. Step 207 would have the user save thecurrent servo settings, with an additional depress value being added tothe current z-axis servo value, into nonvolatile controller and powersupply 8 memory. Step 208 shows the button counter being incremented forthe next button and step 209 checks if the final button has beencalibrated. If not, steps 203 through 208 will be repeated for the nextbutton. If this is the final button, step 210 completes the calibrationprocess.

In another embodiment, the calibration procedure 200 could be furtherautomated using a mobile device equipped with a camera and a specificapplication to take a photograph of the remote control 101 and with thecalibration guide alignment pins 52, 53, 54 and 55 in the photograph tobe used as image reference guides. The application would be used by theuser to identify each remote control 101 button and determine theappropriate angle-axis, r-axis and z-axis servo values to save duringthe calibration process. Additionally, the software application wouldpermit the user to create the duration of every button press specific toeach vehicle or device and create additional commands which would linkmultiple, serial button commands into a single function, such as aremote start command which required one button to be pressed for 0.5sec. followed by a second button to be pressed and held for 2 seconds.

Once calibrated, the user would send a button command from their mobiledevice through the controlling system 100 to the controller and powersupply 8. The flowchart of FIG. 9 illustrates the operate buttonactuator 300 process. Step 301 begins with the command from thecontrolling system 100 identifying the button number and duration ofpress. Step 302 shows retrieving the saved servo values from thecontroller and power supply 8 nonvolatile memory for the angle-axisservo motor 9, r-axis servo motor 20 and z-axis servo motor 22. Step 303shows sending the correct angle-axis value to the angle-axis servo motor9 to rotate the boom support 10 to the correct angle. Step 304 showssending the correct r-axis value to the r-axis servo motor 20 to extendthe sliding boom to the correct length. Step 305 shows sending thecorrect z-axis servo value to the z-axis servo motor 22 to lower thebutton actuator tip 1, thus pressing the remote control button, andinitiating a duration timer. Step 306 checks if the button pressduration has been exceeded. If not, the timer is incremented in step 309and step 306 checks the timer again. Steps 306 and 309 are repeateduntil the timer duration is exceeded. When step 6 exits with the timerduration exceeded, step 307 sends the uppermost button actuator tip 1position value to z-axis servo motor 22 to return the button actuatortip 1 to the uppermost position. Step 308 shows the end of the operatebutton actuator process 300.

Turning now to FIG. 10, illustrated is a high level functional blockdiagram of an exemplary architecture of a system 10 for remoteactuation. For example, a vehicle having an actuation package 800,controlled by a user carrying a portable computing device 100, such as aSmartphone, on his person would be one embodiment of the actuationcomponent 100 and the mobile component 850 of such architecture.

Notably, although the FIG. 10 illustration depicts an actuation package800 and a mobile component 850, it will be understood that not allembodiments of the disclosed system and method require a mobilecomponent 850 and a actuation package 800 to be within a proximate to auser. That is, it is envisioned that certain functionality in anembodiment may be implemented via a remote computing device such as aserver 105. In such embodiments, the actuation package 800 maycommunicate with the server 105 via a communications network 191 withoutneed to communicate 190A with a mobile component 850. In otherembodiments, an actuation package 800 may communicate with either orboth of the server 105 and the mobile component 850. Similarly, in someembodiments, the mobile component 850 may transmit data to and/or fromthe server 105 via link 190B which is implemented over communicationsnetwork 191.

FIG. 12 is a functional block diagram illustrating an exemplary,non-limiting aspect of a portable computing device (“PCD”), such as amobile component 850 and/or a actuation package 800, for implementingthe disclosed methods and systems. The PCD may be in the form of awireless telephone in some embodiments. As shown, the PCD 100, 125includes an on-chip system 102 that includes a multi-core centralprocessing unit (“CPU”) 110 and an analog signal processor 126 that arecoupled together. The CPU 110 may comprise a zeroth core 222, a firstcore 224, and an Nth core 230 as understood by one of ordinary skill inthe art. Further, instead of a CPU 110, a digital signal processor(“DSP”) may also be employed as understood by one of ordinary skill inthe art.

As illustrated in FIG. 11, a display controller 128 and a touch screencontroller 130 are coupled to the digital signal processor 110. A touchscreen display 132 external to the on-chip system 102 is coupled to thedisplay controller 128 and the touch screen controller 130. PCD 100, 125may further include a video encoder 134, e.g., a phase-alternating line(“PAL”) encoder, a sequential couleur avec memoire (“SECAM”) encoder, anational television system(s) committee (“NTSC”) encoder or any othertype of video encoder 134. The video encoder 134 is coupled to themulti-core CPU 110. A video amplifier 136 is coupled to the videoencoder 134 and the touch screen display 132. A video port 138 iscoupled to the video amplifier 136. As depicted in FIG. 6, a universalserial bus (“USB”) controller 140 is coupled to the CPU 110. Also, a USBport 142 is coupled to the USB controller 140. A memory 112, which mayinclude a PoP memory, a cache 116, a mask ROM/Boot ROM, a boot OTPmemory, a DDR memory 115 may also be coupled to the CPU 110. Asubscriber identity module (“SIM”) card 146 may also be coupled to theCPU 110. Further, as shown in FIG. 6, a digital camera 148 may becoupled to the CPU 110. In an exemplary aspect, the digital camera 148is a charge-coupled device (“CCD”) camera or a complementary metal-oxidesemiconductor (“CMOS”) camera.

As further illustrated in FIG. 11, a stereo audio CODEC 150 may becoupled to the analog signal processor 126. Moreover, an audio amplifier152 may be coupled to the stereo audio CODEC 150. In an exemplaryaspect, a first stereo speaker 154 and a second stereo speaker 156 arecoupled to the audio amplifier 152. FIG. 6 shows that a microphoneamplifier 158 may be also coupled to the stereo audio CODEC 150.Additionally, a microphone 160 may be coupled to the microphoneamplifier 158. In a particular aspect, a frequency modulation (“FM”)radio tuner 162 may be coupled to the stereo audio CODEC 150. Also, anFM antenna 164 is coupled to the FM radio tuner 162. Further, stereoheadphones 166 may be coupled to the stereo audio CODEC 150.

FIG. 11 further indicates that a radio frequency (“RF”) transceiver 168may be coupled to the analog signal processor 126. An RF switch 170 maybe coupled to the RF transceiver 168 and an RF antenna 172. As shown inFIG. 6, a keypad 174 may be coupled to the analog signal processor 126.Also, a mono headset with a microphone 176 may be coupled to the analogsignal processor 126. Further, a vibrator device 178 may be coupled tothe analog signal processor 126. FIG. 6 also shows that a power supply188, for example a battery, is coupled to the on-chip system 102 througha power management integrated circuit (“PMIC”) 180. In a particularaspect, the power supply 188 includes a rechargeable DC battery or a DCpower supply that is derived from an alternating current (“AC”) to DCtransformer that is connected to an AC power source. In anotherparticular aspect, the power supply 188 includes a kineticallyrechargeable DC battery.

The CPU 110 may also be coupled to one or more internal, on-chip thermalsensors 157A as well as one or more external, off-chip thermal sensors157B and physiological sensors 159. The on-chip thermal sensors 157A maycomprise one or more proportional to absolute temperature (“PTAT”)temperature sensors that are based on vertical PNP structure and areusually dedicated to complementary metal oxide semiconductor (“CMOS”)very large-scale integration (“VLSI”) circuits. The off-chip thermalsensors 157B may comprise one or more thermistors. The thermal sensors157 may produce a voltage drop that is converted to digital signals withan analog-to-digital converter (“ADC”) controller (not shown). However,other types of thermal sensors 157 may be employed.

FIG. 12 is a schematic diagram illustrating an exemplary softwarearchitecture 700 for the disclosed embodiments. As illustrated in FIG.7, the CPU or digital signal processor 110 is coupled to the memory 112via main bus 211. The memory 112 may reside within a mobile component850, a actuation package 800 or a combination thereof. Similarly, itwill be understood that the actuation module 101 and the CPU 110 mayreside within a mobile component 850, a actuation package 800 or acombination thereof.

The CPU 110, as noted above, is a multiple-core processor having N coreprocessors. That is, the CPU 110 includes a first core 222, a secondcore 224, and an N^(th) core 230. As is known to one of ordinary skillin the art, each of the first core 222, the second core 224 and theN^(th) core 230 are available for supporting a dedicated application orprogram. Alternatively, one or more applications or programs may bedistributed for processing across two or more of the available cores.

The CPU 110 may receive commands from the actuation module(s) 101 thatmay comprise software and/or hardware. If embodied as software, themodule(s) 101 comprise instructions that are executed by the CPU 110that issues commands to other application programs being executed by theCPU 110 and other processors.

The first core 222, the second core 224 through to the Nth core 230 ofthe CPU 110 may be integrated on a single integrated circuit die, orthey may be integrated or coupled on separate dies in a multiple-circuitpackage. Designers may couple the first core 222, the second core 224through to the N^(th) core 230 via one or more shared caches and theymay implement message or instruction passing via network topologies suchas bus, ring, mesh and crossbar topologies.

Bus 211 may include multiple communication paths via one or more wiredor wireless connections, as is known in the art and described above inthe definitions. The bus 211 may have additional elements, which areomitted for simplicity, such as controllers, buffers (caches), drivers,repeaters, and receivers, to enable communications. Further, the bus 211may include address, control, and/or data connections to enableappropriate communications among the aforementioned components.

When the logic used by the PCD (e.g., actuation component/mobilecomponent) 800/850 is implemented in software, as is shown in FIG. 12,it should be noted that one or more of startup logic 250, managementlogic 260, actuation interface logic 270, applications in applicationstore 280 and portions of the file system 290 may be stored on anycomputer-readable medium for use by, or in connection with, anycomputer-related system or method. In the context of this document, acomputer-readable medium is an electronic, magnetic, optical, or otherphysical device or means that can contain or store a computer programand data for use by or in connection with a computer-related system ormethod. The various logic elements and data stores may be embodied inany computer-readable medium for use by or in connection with aninstruction execution system, apparatus, or device, such as acomputer-based system, processor-containing system, or other system thatcan fetch the instructions from the instruction execution system,apparatus, or device and execute the instructions. In the context ofthis document, a “computer-readable medium” can be any means that canstore, communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.

The computer-readable medium can be, for example but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, device, or propagation medium. Morespecific examples (a non-exhaustive list) of the computer-readablemedium would include the following: an electrical connection(electronic) having one or more wires, a portable computer diskette(magnetic), a random-access memory (RAM) (electronic), a read-onlymemory (ROM) (electronic), an erasable programmable read-only memory(EPROM, EEPROM, or Flash memory) (electronic), an optical fiber(optical), Flash, and a portable compact disc read-only memory (CDROM)(optical). Note that the computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, for instance via opticalscanning of the paper or other medium, then compiled, interpreted orotherwise processed in a suitable manner if necessary, and then storedin a computer memory. Disk and disc, as used herein, includes compactdisc (“CD”), laser disc, optical disc, digital versatile disc (“DVD”),floppy disk and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

In an alternative embodiment, where one or more of the startup logic250, management logic 260 and perhaps the actuation interface logic 270are implemented in hardware, the various logic may be implemented withany or a combination of the following technologies, which are each wellknown in the art: a discrete logic circuit(s) having logic gates forimplementing logic functions upon data signals, an application specificintegrated circuit (ASIC) having appropriate combinational logic gates,a programmable gate array(s) (PGA), a field programmable gate array(FPGA), etc.

The memory 112 is a non-volatile data storage device such as a flashmemory or a solid-state memory device. Although depicted as a singledevice, the memory 112 may be a distributed memory device with separatedata stores coupled to the digital signal processor 110 (or additionalprocessor cores).

The startup logic 250 includes one or more executable instructions forselectively identifying, loading, and executing a select program foractuation of the remote control of a vehicle. The startup logic 250 mayidentify, load and execute an actuation program. An exemplary selectprogram may be found in the program store 296 of the embedded filesystem 290. The exemplary select program, when executed by one or moreof the core processors in the CPU 110 may operate in accordance with oneor more signals provided by the actuation module 101 to start theprogram.

The management logic 260 includes one or more executable instructionsfor terminating a program on one or more of the respective processorcores, as well as selectively identifying, loading, and executing a moresuitable replacement program. The management logic 260 is arranged toperform these functions at run time or while the PCD 100 is powered andin use by an operator of the device. A replacement program, which may becustomized by a user in some embodiments, may be found in the programstore 296 of the embedded file system 290.

The interface logic 270 includes one or more executable instructions forpresenting, managing and interacting with external inputs to observe,configure, or otherwise update information stored in the embedded filesystem 290. In one embodiment, the interface logic 270 may operate inconjunction with manufacturer inputs received via the USB port 142.These inputs may include one or more programs to be deleted from oradded to the program store 296. Alternatively, the inputs may includeedits or changes to one or more of the programs in the program store296. Moreover, the inputs may identify one or more changes to, or entirereplacements of one or both of the startup logic 250 and the managementlogic 260.

The interface logic 270 enables a manufacturer to controllably configureand adjust an end user's experience under defined operating conditionson the PCD 800/850. When the memory 112 is a flash memory, one or moreof the startup logic 250, the management logic 260, the interface logic270, the application programs in the application store 280 orinformation in the embedded file system 290 may be edited, replaced, orotherwise modified. In some embodiments, the interface logic 270 maypermit an end user or operator of the PCD 800/850 to search, locate,modify or replace the startup logic 250, the management logic 260,applications in the application store 280 and information in theembedded file system 290. The operator may use the resulting interfaceto make changes that will be implemented upon the next startup of thePCD 800/850. Alternatively, the operator may use the resulting interfaceto make changes that are implemented during run time.

The embedded file system 290 includes a hierarchically arrangedactuation store 292. In this regard, the file system 290 may include areserved section of its total file system capacity for the storage ofinformation for the configuration and management of the variousalgorithms used by the PCD 800/850.

Systems, devices and methods for the remote actuation system have beendescribed using detailed descriptions of embodiments thereof that areprovided by way of example and are not intended to limit the scope ofthe disclosure. The described embodiments comprise different features,not all of which are required in all embodiments of a remote actuationsystem. Some embodiments of a remote actuation system utilize only someof the features or possible combinations of the features. Variations ofembodiments of a remote actuation system that are described andembodiments of a remote actuation system comprising differentcombinations of features noted in the described embodiments will occurto persons of the art.

It will be appreciated by persons skilled in the art that systems,devices and methods for the provision of remote actuation system is notlimited by what has been particularly shown and described herein above.Rather, the scope of systems, devices and methods for the provision ofremote actuation system is defined by the claims that follow.

Certain steps in the processes or process flows described in thisspecification naturally precede others for the description to functionas described. However, the description is not limited to the order ofthe steps described if such order or sequence does not alter thefunctionality of the description. That is, it is recognized that somesteps may performed before, after, or parallel (substantiallysimultaneously with) other steps without departing from the scope andspirit of the description. In some instances, certain steps may beomitted or not performed without departing from the description.Further, words such as “thereafter”, “then”, “next”, etc. are notintended to limit the order of the steps. These words are simply used toguide the reader through the description of the exemplary method.

Additionally, one of ordinary skill in programming is able to writecomputer code or identify appropriate hardware and/or circuits toimplement the disclosed description without difficulty based on the flowcharts and associated description in this specification, for example.

Therefore, disclosure of a particular set of program code instructionsor detailed hardware devices is not considered necessary for an adequateunderstanding of how to make and use the description. The inventivefunctionality of the claimed computer implemented processes is explainedin more detail in the above description and in conjunction with thedrawings, which may illustrate various process flows.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted as one or more instructions or code on a computer-readablemedium. Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that may be accessed by a computer. By way of example,and not limitation, such computer-readable media may comprise RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that may be used tocarry or store desired program code in the form of instructions or datastructures and that may be accessed by a computer.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (“DSL”), or wireless technologies such asinfrared, radio, and microwave, then the coaxial cable, fiber opticcable, twisted pair, DSL, or wireless technologies such as infrared,radio, and microwave are included in the definition of medium.

Disk and disc, as used herein, includes compact disc (“CD”), laser disc,optical disc, digital versatile disc (“DVD”), floppy disk and blu-raydisc where disks usually reproduce data magnetically, while discsreproduce data optically with lasers. Combinations of the above shouldalso be included within the scope of computer-readable media.

Therefore, although selected aspects have been illustrated and describedin detail, it will be understood that various substitutions andalterations may be made therein without departing from the spirit andscope of the present description, as defined by the following claims.

What is claimed is:
 1. A machine to actuate one or more buttons of aremote control, the machine comprising: a rotatable pivot secured to abase; a boom comprising a first end and second end, the boom rotatablymounted on the rotatable pivot at the first end and reversiblyextendable from the pivot; an actuator tip fixedly mounted on the secondend, and wherein the pivot, the boom and the actuator are configured tomove the tip to a position associated with a particular button and tolower and raise the tip to engage the particular button of the remotecontrol.
 2. The machine of claim 1, further comprising a gear coaxiallymounted on the pivot and engaged with a first drive gear operably linkedto a first servomotor driveshaft.
 3. The machine of claim 1, furthercomprising a gear coaxially mounted on the first end and engaged with asecond drive gear operably linked to a second servomotor driveshaft. 4.The machine of claim 1, wherein the first end is slidably engaged withthe second end.
 5. The machine of claim 4, wherein a pinion is mountedon the first end, the pinion operably linked to a third servomotordriveshaft, and wherein the pinion engages gearing means operable toextend the boom upon operation of the third servomotor driveshaft. 6.The machine of claim 1, wherein the actuator further comprises a rackgear engaged with an actuator pinion and fourth servomotor driveshaftaxially linked to the actuator pinion.
 7. The machine of claim 1,further comprising an electronic controller in electronic communicationwith the first, second, third and fourth servomotors.
 8. The machine ofclaim 7, further comprising a programmable hardware module in electroniccommunication with the electronic controller.
 9. The machine of claim 7,further comprising a programmable software module in electroniccommunication with the electronic controller.
 10. The machine of claim1, wherein the pivot, the boom and the actuator are configured to movethe tip to a position associated with a second particular button and tolower and raise the tip to engage the particular button of the remotecontrol.
 11. The machine of claim 10, wherein the pivot, the boom andthe actuator are configured to lower the tip for a particular durationof time and then raise the tip to engage the particular button of theremote control and then to lower the tip for a second particularduration of time and then raise the tip to engage the second particularbutton.
 12. The machine of claim 11, wherein the particular button andthe second particular button can being either the same button ordifferent buttons.
 13. The machine of claim 1, wherein the pivot, theboom and the actuator are configured to move the tip to a positionassociated with a next button and to lower and raise the tip to engagethe next button of the remote control.
 14. The machine of claim 1,wherein the pivot, the boom and the actuator are configured to lower thetip for a particular duration of time and then raise the tip to engagethe particular button of the remote control.
 15. A method of remotelyactuating the buttons of a remote control, wherein the remote control ismounted within an actuation machine, the method comprising the actionsof: obtaining calibration data to identify the locations of the buttonsof the remote control and store the identify as location data; receivinga button actuation command; retrieve the location data for a particularbutton identified in the actuation command; moving a rotatable pivot andboom to a position based on the location data; sending a signal to anactuator located on a distal end of the boom, the signal causing theactuator to move a tip to touch and press the particular button for aperiod of time and then release the particular button.
 16. The method ofclaim 15, wherein the action of obtaining calibration data comprisesretrieving the data from a memory element.
 17. The method of claim 15,wherein the action of obtaining calibration data comprises receiving adata file into a memory element of the actuation machine.
 18. The methodof claim 15, wherein the action of obtaining calibration data comprisescausing the rotatable pivot and boom to be positioned over one or morebuttons of the remote control and recording the location data, andcausing the actuator to actuate the button by advancing the tip andrecording the advancement data.
 19. A computer program productcomprising a computer readable medium having a computer readable codeembodied therein, the computer readable program code adapted to beexecuted to implement a method of remotely actuating the buttons of aremote control comprising: mounting a remote control with actuablebuttons in proximity to a machine to actuate buttons of a remote controlcomprising: a rotatable pivot secured to a base; a boom comprising afirst end and second end, the boom rotatably mounted on the rotatablepivot at the first end and reversibly extendable from the pivot; anactuator fixedly mounted on the second end, and wherein the pivot, theboom and the actuator are configurable to raise and lower a tip toengage the buttons of the remote control; and operating a computer thatexecutes the computer readable program code.
 20. A machine to actuateone or more buttons of a remote control, the machine comprising: a pivotsecured to a base; a boom comprising a first end and second end, theboom rotatably mounted on the pivot at the first end; an actuator tipslidably mounted on the boom proximate the second end and wherein thepivot, the boom and the actuator are configured to move the tip to aposition associated with a particular button and to lower and raise thetip to engage the particular button of the remote control.